Radial gesture navigation

ABSTRACT

Systems and methods for radial gesture navigation are provided. In example embodiments, user input data is received from a user device. The user input data indicates a continuous physical user interaction associated with a display screen of the user device. An initial point and a current point are detected from the user input data. A radius distance for a circle that includes the current point and is centered about the initial point is determined. An action is selected from among multiple actions based on the radius distance being within a particular range among successive ranges along a straight line that starts at the initial point and extends through the circle. Each range among the successive ranges corresponds to a particular action among the multiple actions. The selected action is performed in response to detecting a completion of the continuous physical user interaction.

PRIORITY CLAIM

This application is a continuation of and claims the benefit of priorityof U.S. patent application Ser. No. 14/740,843, filed on Jun. 16, 2015,which is hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

Embodiments of the present disclosure relate generally to user inputnavigation and, more particularly, but not by way of limitation, toradial gesture navigation.

BACKGROUND

Touchscreen displays and similar point-based input schemes are a popularmeans of receiving user input amongst mobile devices, wearable devices,and the like. Such user input schemes typically rely upon a uservisually identifying and interpreting a particular user interfaceelement in conjunction with manipulating the user interface element toprovide input. For instance, a conventional user interface design for atouchscreen may include multiple interactive buttons, where each buttonperforms an action when activated by the user. Over time, a user canbecome efficient at using a particular user interface design via motorlearning resulting from repeated practice with the particular userinterface design, provided the user interface design does not change.However, these types of user interface designs are susceptible todrawbacks such as a large display footprint for user interface elementsand a diminished ability for the user to become efficient through motorlearning when there are changes in, or variations of, the user interfacedesign.

BRIEF DESCRIPTION OF THE DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present disclosure and should not be considered aslimiting its scope.

FIG. 1 is a block diagram illustrating a networked system, according tosome example embodiments.

FIG. 2 is a block diagram illustrating an example embodiment of agesture navigation system, according to some example embodiments.

FIG. 3 is a user interface diagram depicting an example gesture on anexample device, according to some example embodiments.

FIG. 4 is a flow diagram illustrating an example method for radialgesture navigation, according to some example embodiments.

FIG. 5 is a diagram depicting detection of aspects of a gesture at anexample touchscreen, according to some example embodiments.

FIG. 6 is a diagram depicting aspects of various gestures, according tosome example embodiments.

FIG. 7 is a diagram depicting various gestures, according to someexample embodiments.

FIG. 8 is a flow diagram illustrating example operations for presentinga visual indication of an action associated with a gesture, according tosome example embodiments.

FIG. 9 is a user interface diagram depicting an example visualindication of an action displayed on an example device, according tosome example embodiments.

FIG. 10 is a flow diagram illustrating example operations for detectingcertain aspects of a gesture, according to some example embodiments.

FIG. 11 is a user interface diagram depicting example data used todetect a gesture, according to some example embodiments.

FIG. 12 is a user interface diagram depicting an example of performingan action associated with a particular item using a gesture, accordingto some example embodiments.

FIG. 13 is a user interface diagram depicting an example of performingan action using a gesture, according to some example embodiments.

FIG. 14 is a diagram illustrating an example of initiating a livestreaming session of media data being captured in real time by a userdevice, according to some example embodiments.

FIG. 15 is a flow diagram illustrating an example method for switchingbetween a recording session and a live streaming session, according tosome example embodiments.

FIG. 16 is a user interface diagram depicting an example of initiating arecording session with an option to switch to live streaming session,according to some example embodiments.

FIG. 17 is a user interface diagram depicting an example of switchingfrom a recording session to a live streaming session, according to someexample embodiments.

FIG. 18 is a user interface diagram depicting an example of initiating asustained recording session with a gesture, according to some exampleembodiments.

FIG. 19 is a flow diagram illustrating an example method for adjusting,altering, or otherwise modifying parameters, characteristics, orsettings of a recording session, a live streaming session, or a mediapresentation session via a gesture, according to some exampleembodiments.

FIG. 20 is a user interface diagram depicting an example of initiatingthe live streaming session and modifying a characteristic of the livestreaming session via a particular gesture, according to some exampleembodiments.

FIG. 21 is a user interface diagram depicting a further example ofadjusting, altering, or otherwise modifying parameters, characteristics,or settings of a recording session, a live streaming session, or a mediapresentation session via a particular gesture, according to some exampleembodiments.

FIG. 22 is a block diagram illustrating an example of a softwarearchitecture that may be installed on a machine, according to someexample embodiments.

FIG. 23 is a block diagram presenting a diagrammatic representation of amachine in the form of a computer system within which a set ofinstructions may be executed for causing the machine to perform any ofthe methodologies discussed herein, according to an example embodiment.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the disclosure. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art, that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques are not necessarily shown in detail.

Many computing devices, such as mobile devices and wearable devices,employ a point-based user input scheme as a primary means of receivinguser input. For example, smart phones often include a touch-sensitivedisplay that can receive point-based touch input from a user. Thesetouch-sensitive displays or touchscreens detect user input dataresulting from physical contact with the display such as contact from auser's finger, a stylus, or a pen. The user input data can includepositional data, force data (e.g., force of a touch on the touchscreen),temporal data (e.g., timing of touchscreen touches or events), and otherdata. Other input schemes include the use of motion capture to trackpositional information, such as a motion of a user's hand, fingers, or astylus in two or three dimensions.

Conventional user interface designs employ visual user interfaceelements positioned on the display that the user visually identifies andmanipulates. Over time, users become adept at interacting with theseuser interfaces through repeated practice. One drawback to this type ofapproach is that a change in layout or positioning of an interactiveuser interface element reduces user efficiency as a user relearns how tointeract with the new design. Another drawback to this type of approachis that providing more functionality uses more display spaces (e.g.,more buttons to perform more functions). Designers of these conventionaluser interfaces often face a trade-off between a spacious, easy-to-usedesign and providing robust functionality with many user interfaceelements.

In various example embodiments, a radial slide gesture provides anintuitive, space-efficient technique for receiving and interpreting userinput. In an example embodiment, a gesture navigation system receivesuser input data that indicates a continuous physical user interaction(herein, also referred to as a gesture) associated with a display screenof a user device. For instance, the user device may be a smart phonethat includes a touchscreen display to track, monitor, or otherwisecapture touch data from user input. The gesture navigation systemdetects an initial point from the user input data such as when the userbegins a particular gesture. Subsequently, the gesture navigation systemdetects a current point from the user input data. The gesture navigationsystem then determines a radius distance based on the initial point andthe current point. For instance, the radius distance is determined froma circle that includes the current point and is centered about theinitial point. The gesture navigation system selects an action based onthe radius distance. For example, if the radius distance falls within aparticular range, the gesture navigation system selects an actioncorresponding to the particular range. Once the gesture navigationsystem selects the action, the gesture navigation system performs orinvokes the selected action upon termination of the gesture (e.g., theuser lifting their finger from the touchscreen display to indicatecompletion or end of the gesture).

In some embodiments, the gesture navigation system presents a visualindication of an available action as the current point of the gesturetransgresses a boundary of a particular range for the available action.For example, the visual indication can include a description of theaction that is available to perform (e.g., a textual or graphicaldescription).

In further example embodiments, the gesture navigation system detects aninitiation of the radial slide gesture based on a press and holdgesture. For example, the user may touch the touchscreen of the userdevice and substantially refrain from moving the current point of thetouch for a threshold period of time to initiate the radial slidegesture. After the gesture navigation system detects the press and holdgesture, the gesture navigation system can detect the user performingthe radial slide gesture to select a particular action among multipleactions. In this way, the radial slide gesture is first affirmativelyinitiated by the user to prevent an undesired or accidental selection ofan action via the radial slide gesture. In certain embodiments, aportion of the user interface is deactivated after the radial slidegesture is initiated to prevent user interface interactions other thanthe radial slide gesture.

In still further embodiments, the gesture navigation system receives anindication of a designated user interface element and the gesturenavigation system performs the selected action in association with thedesignated user interface element. For instance, the designated userinterface element may be an indication of a particular individual on afriends list. In this instance, the selected action may be to send amessage or initiate a chat session with the particular individual. Insome embodiments, the gesture navigation system determines thedesignated user interface element based on the initial point. In thisway, the radial slide gesture can be used to provide multiple actionsfor a user interface element located anywhere on the display.

Accordingly, techniques described herein allow for a multiple-actionuser input that is intuitive and provides interface design freedom sinceany location on the display can be designated for one or more actions.These techniques are motor skill driven and demand less reliance on theuser visually interpreting a user interface. As a result, efficienciesdeveloped by the user can more easily be retained since the radial slidegesture operates similarly across different display layouts. Thus, theradial slide gesture improves user experience by providing a multitudeof actions while being intuitive and predictable, even for unfamiliaruser interface layouts.

FIG. 1 is a network diagram depicting a network system 100 having aclient-server architecture configured for exchanging data over anetwork, according to one embodiment. For example, the network system100 may be a messaging system where clients communicate and exchangedata within the network system 100. The data may pertain to variousfunctions (e.g., sending and receiving text and media communication,determining geolocation, etc.) and aspects associated with the networksystem 100 and its users. Although illustrated herein as client-serverarchitecture, other embodiments may include other network architectures,such as peer-to-peer or distributed network environments.

As shown in FIG. 1, the network system 100 includes a social messagingsystem 130. The social messaging system 130 is generally based on athree-tiered architecture, comprising an interface layer 124, anapplication logic layer 126, and a data layer 128. As is understood byskilled artisans in the relevant computer and Internet-related arts,each module, system, or engine shown in FIG. 1 represents a set ofexecutable software instructions and the corresponding hardware (e.g.,memory and processor) for executing the instructions. To avoid obscuringthe inventive subject matter with unnecessary detail, various functionalmodules and engines that are not germane to conveying an understandingof the inventive subject matter have been omitted from FIG. 1. Ofcourse, additional functional modules and engines may be used with asocial messaging system, such as that illustrated in FIG. 1, tofacilitate additional functionality that is not specifically describedherein. Furthermore, the various functional modules and engines depictedin FIG. 1 may reside on a single server computer, or may be distributedacross several server computers in various arrangements. Moreover,although the social messaging system 130 is depicted in FIG. 1 as athree-tiered architecture, the inventive subject matter is by no meanslimited to such an architecture.

As shown in FIG. 1, the interface layer 124 comprises a interface module(e.g., a web server) 140, which receives requests from variousclient-computing devices and servers, such as client devices 110 eachexecuting a client application 112, and third party servers 120 eachexecuting a third party application 122. In response to receivedrequests, the interface module 140 communicates appropriate responses torequesting devices via a network 104. For example, the interface module140 can receive requests such as Hypertext Transfer Protocol (HTTP)requests, or other web-based Application Programming Interface (API)requests.

The client devices 110 can execute conventional web browser applicationsor applications (also referred to as “apps”) that have been developedfor a specific platform to include any of a wide variety of mobilecomputing devices and mobile-specific operating systems (e.g., IOS™,ANDROID™, WINDOWS®PHONE). In an example, the client devices 110 areexecuting the client application 112. The client application 112 canprovide functionality to present information to a user 106 andcommunicate via the network 104 to exchange information with the socialmessaging system 130. Each client device 110 can comprise a computingdevice that includes at least a display and communication capabilitieswith the network 104 to access the social messaging system 130. Theclient devices 110 comprise, but are not limited to, remote devices,work stations, computers, general purpose computers, Internetappliances, hand-held devices, wireless devices, portable devices,wearable computers, cellular or mobile phones, personal digitalassistants (PDAs), smart phones, tablets, ultrabooks, netbooks, laptops,desktops, multi-processor systems, microprocessor-based or programmableconsumer electronics, game consoles, set-top boxes, network PCs,mini-computers, and the like. The user 106 can be a person, a machine,or other means of interacting with the client devices 110. In someembodiments, the user 106 interacts with the social messaging system 130via the client devices 110.

As shown in FIG. 1, the data layer 128 has a database server 132 thatfacilitates access to an information storage repository or database 134.The database 134 is a storage device that stores data such as memberprofile data, social graph data (e.g., relationships between members ofthe social messaging system 130), and other user data.

An individual can register with the social messaging system 130 tobecome a member of the social messaging system 130. Once registered, amember can form social network relationships (e.g., friends, followers,or contacts) on the social messaging system 130 and interact with abroad range of applications provided by the social messaging system 130.

The application logic layer 126 includes one or more application logicmodule 150, which, in conjunction with the interface module 140,generates various user interfaces using data retrieved from various datasources or data services in the data layer 128. The application logicmodule 150 can be used to implement the functionality associated withvarious applications, services, and features of the social messagingsystem 130. For instance, a social messaging application can beimplemented with the application logic module 150. The social messagingapplication provides a messaging mechanism for users of the clientdevices 110 to send and receive messages that include text and mediacontent such as pictures and video. The client devices 110 may accessand view the messages from the social messaging application for aspecified period of time (e.g., limited or unlimited). In an example, aparticular message is accessible to a message recipient for a predefinedduration (e.g., specified by a message sender) that begins when theparticular message is first accessed. After the predefined durationelapses, the message is deleted and is no longer accessible to themessage recipient. Of course, other applications and services may beseparately embodied in their own application server module.

As illustrated in FIG. 1, the social messaging system 130 includes agesture navigation system 160. In various embodiments, the gesturenavigation system 160 can be implemented as a standalone system and isnot necessarily included in the social messaging system 130. In someembodiments, the client devices 110 include a portion of the gesturenavigation system 160 (e.g., a portion of the gesture navigation system160 included independently or in the client application 112). Inembodiments where the client devices 110 includes a portion of thegesture navigation system 160, the client devices 110 can work alone orin conjunction with the portion of the gesture navigation system 160included in a particular application server or included in the socialmessaging system 130.

FIG. 2 is a block diagram 200 of the gesture navigation system 160. Thegesture navigation system 160 is shown to include a communication module210, a user interface module 220, a gesture module 230, an action module240, an invocation module 250, and a sensor module 260. All or some ofthe modules 210-260 communicate with each other, for example, via anetwork coupling, shared memory, and the like. Each module of themodules 210-260 can be implemented as a single module, combined intoother modules, or further subdivided into multiple modules. Othermodules not pertinent to example embodiments can also be included, butare not shown.

The communication module 210 provides various communicationsfunctionality. For example, the communication module 210 can facilitateperforming a particular action by communicating with the socialmessaging system 130 or the third party server 120. The communicationmodule 210 exchanges network communications with the database server132, the client devices 110, and the third party server 120. Theinformation retrieved by the communication module 210 includes dataassociated with the user 106 (e.g., member profile data from an onlineaccount or social network service data) or other data to facilitate thefunctionality described herein.

The user interface module 220 provides various presentation and userinterface functionality operable to interactively present information toand receive information from the user (e.g., user 106). For instance,the user interface module 220 is utilizable to present a visualindication of an action to be performed or alter a user interface toemphasize a particular aspect of the user interface. In variousembodiments, the user interface module 220 presents or causespresentation of information (e.g., visually displaying information on ascreen, acoustic output, haptic feedback, etc.). The process ofinteractively presenting information is intended to include the exchangeof information between a particular device and the user. The user mayprovide input to interact with the user interface in many possiblemanners, such as alphanumeric, point based (e.g., cursor or tactile), orother input (e.g., touch screen, light sensor, infrared sensor,biometric sensor, microphone, gyroscope, accelerometer, or othersensors). The user interface module 220 provides many other userinterfaces to facilitate functionality described herein. The term“presenting” as used herein is intended to include communicatinginformation or instructions to a particular device that is operable toperform presentation based on the communicated information orinstructions.

The gesture module 230 provides functionality to detect aspects of aparticular gesture from the user input data. For example, the gesturemodule 230 detects an initial point, a current point, a terminal point,satisfaction of a time threshold, satisfaction of a distance threshold,a discontinuity in a gesture, and other aspects of a particular gesture.In a specific example, the gesture module 230 detects a completion ortermination of a gesture based on the user releasing their finger from atouchscreen display.

The action module 240 provides functionality to select and determineactions associated with a particular gesture. For example, the actionmodule 240 identifies a particular action to perform based on acharacteristic of a particular gesture such as a distance of a slide ordrag gesture. In some examples, the action module 240 determines theaction to perform based on the gesture in conjunction with a designateduser interface element. For instance, the action module 240 determines aspecific action for a particular designated user interface element and adifferent action for a different user interface element.

The invocation module 250 provides functionality to invoke a particularaction. For example, an action may be performed locally (e.g., localfile management) at the user device or invoked by communicating with aserver or system (e.g., sending a message to a member of the socialmessaging service) such as the social messaging system 130. In aspecific example, the invocation module 250 establishes a chat sessionbetween the user of the user device and another member of the socialmessaging service.

The sensor module 260 provides various sensor functionality such astouchscreen display input monitoring. In a specific example, the sensormodule 260 monitors touchscreen display input such as positionalinformation (e.g., x and y coordinates), force information, and timinginformation (e.g., a timeline associated with the positional or forceinformation). The sensor module 260 can monitor sensor data via eventdriven update (e.g., receive touch data as it occurs), polling at aparticular sampling rate, or continuously monitor output from aparticular sensor.

FIG. 3 is a user interface diagram 300 depicting an example gesturebeing performed on an example device (e.g., a smart phone) displayingexample user interface 310. In the user interface 310, a user 320 isperforming a radial slide gesture 350 to cause invocation of an actionassociated with user interface element 330. In the diagram 300, thesensor module 260 receives user input data that indicates the user 320is physically touching a touchscreen display of the user device as shownby touch 340. The gesture module 230 detects an initial point and acurrent point of the radial slide gesture 350 and determines a radiusdistance for the radial slide gesture 350.

The action module 240 determines an action based on the radius distanceof the radial slide gesture 350. For example, the action module 240selects a first, second, or third action, 370, 380, or 390 respectively,when the radius distance is within a particular range corresponding toone of those actions. For example, the actions 370, 380, and 390 mayperform a function associated with the designated user interface element330. In a specific example, the first action 370 may ‘like’ or designatesome item as a ‘favorite’ of the user, the second action 380 mayinitiate a text-based chat, and the third action 390 may initiate avideo chat with a particular user associated with the designated userinterface element 330. Put another way, concentric circles centeredabout the initial point can define boundaries for different ranges. Theaction module 240 selects an action for a particular range when thecurrent point is within the boundaries for a particular range (e.g.,greater than a first concentric circle boundary and less than a secondconcentric circle boundary that is consecutive to the first concentriccircle boundary). After the action module 240 selects the action, theinvocation module 250 performs, or facilitates performing, the selectedaction in response to detecting a completion of the radial slide gesture350. For example, the gesture module 230 detects termination orcompletion of a radial slide gesture 350 when the user 320 releases orlifts their finger from the touchscreen. In some embodiments, the usercancels the radial slide gesture 350 (shown in the diagram 300 as cancelgesture 360). i.e., gives an instruction to perform no action, byterminating the radial slide gesture 350 within a distance of theinitial point or beyond a particular distance or off screen.

In some example embodiments, the gesture module 230 initiates the radialslide gesture 350 or radial slide mode only after detecting a ‘hold’gesture. For instance, the user 320 touches the touchscreen at thelocation of the user interface element 330 and substantially refrainsfrom moving the current point of the touch 340 for a threshold period oftime (e.g., 0.75 seconds). That is to say, the gesture module 230detects the hold gesture when a hold time measure, beginning when thegesture module 230 detects the user first touching the touchscreen orwhen the current point is substantially not moving, exceeds thethreshold period of time. After the threshold period of time expires,the radial slide gesture 350 is initiated. In some example embodiments,the gesture module 230 resets a hold time measure if the user moves thecurrent point beyond a hold threshold distance (e.g., 0.2 inches oroutside a boundary of a particular user interface element such as avirtual button) such as when the user does not substantially refrainingfrom moving the current point. In other embodiments, the gesture module230 does not reset the hold time measure and the hold gesture cannot becompleted once the user moves the current point beyond a hold thresholddistance. In these embodiments, the user performs the hold gesture byfirst lifting their finger from the touchscreen to reset the hold timemeasure and subsequently touching the touchscreen and perform anotherhold gesture. In some example embodiments, the user interface module 220causes presentation of a visual indication that the radial slide mode isactive after the hold gesture has been completed (e.g., a change inbackground color of a user interface on the touchscreen or a graphicalor textual description indicating a current mode or successfulcompletion of the hold gesture).

In some instances, the user 320 performs the radial slide gesture 350 asa continuation, or in succession, of the hold gesture (e.g., the user320 remains in continuous physical contact with the touchscreenthroughout the hold gesture and the radial slide gesture 350). Thus, thegesture module 230 can detect various combinations of successivegestures that are performed in series or, in some instances, gesturesthat are performed in parallel. The purpose of first initiating theradial slide gesture 350 is to prevent undesired user interfaceinteraction and allow the user 320 to normally interact with theunderlying user interface without triggering an action invocation via aparticular radial slide gesture. Once the radial slide mode isinitiated, the gesture module 230 can detect the user 320 performing aslide radially outward from the user interface element 330. The holdgesture may also function to designate a particular user interfaceelement located at the initial point. The action module 240 thenidentifies action based on the designated user interface element.

In a specific example, the user interface 310 includes a list ofcontacts. The user 320 performs the radial slide gesture 350 to invokean action associated with one of the contacts in the list of contact.For instance, the user 320 initiates a chat session, sends a message, orremoves a contact from the list by performing the radial slide gesture350 with an initial point being located at a particular contact in thelist of contacts. In this way, the user 320 can quickly perform one ofmultiple actions associated with a user interface element anywhere onthe display without the need of a button or another conventional inputtechnique being on the display.

FIG. 4 is a flow diagram illustrating an example method 400 forreceiving and interpreting a user input such as a gesture. Theoperations of method 400 are performed by components of the gesturenavigation system 160, and are so described below for the purposes ofillustration.

At operation 410, the sensor module 260 receives user input data thatindicates a continuous physical user interaction or gesture associatedwith a display screen of the user device. For example, the sensor module260 continuously or periodically receives or retrieves user input datafrom a touchscreen. In various embodiments, the user input dataindicates positional, force, and temporal data resulting from the userphysically touching the touchscreen.

To illustrate the concepts of operation 410. FIG. 5 is a diagram 500which depicts user input data detected by the sensor module 260 and thegesture module 230. In the diagram 500, a user 504 performs a physicaltouch 506 on a touchscreen 502. In an example embodiment, the sensormodule 260 receives the user input data that comprises a series ofpoints in time corresponding to physical user input (e.g., the touch506). For instance, points 508 and 510 are example points of aparticular user gesture that the user 504 is currently performing at thetouchscrecn 502. In the diagram 500, the points 508 arc points that havealready occurred and points 510 are points that may occur when the user504 completes the gesture. In an embodiment, each of the points 508 and510 correspond to user input data such as touch data 512. As shown inthe diagram 500, the touch data 512 comprises coordinate data for points(e.g., x and y coordinates), force data (e.g., pressure the user 504 maybe applying to the touchscreen 502 at a particular point), temporal data(e.g., a timestamp for each point or indication of an order in which thepoints occurred in time). Although the diagram 500 shows the user inputdata or touch data 512 including coordinate points, it will beappreciated that the sensor module 260 can receive other types ofpositional data or touch data and the gesture module 230 can derivecoordinate data from the other types of data.

Turning back to FIG. 4, at operation 420, the gesture module 230 detectsan initial point or initial position from the user input data. In anembodiment, the initial point is a spatial point corresponding to abeginning of the continuous physical user interaction or gesture. Thatis to say, the initial point is a starting point on the touchscreen of aparticular user gesture. For example, the initial point is the locationon the touchscreen display where the user starts the radial slidegesture.

At operation 430, the gesture module 230 detects a current point fromthe user input data. In an embodiment, the current point is a spatialpoint corresponding to a current state of the continuous physical userinteraction or gesture. In some embodiments, the sensor module 260receives the user input data in real time or substantially real time.The current point corresponds to the current state of the user gestureor user interaction with the user device at a current moment in time.For instance, the current point is the location on the touchscrecndisplay that the user is currently touching.

To illustrate the concepts of operations 420 and 430, FIG. 6 is adiagram 600 depicting aspects of various gestures 608. Similar to FIG. 5discussed above, in the diagram 600, a user 604 performs a physicaltouch 606 on a touchscreen 602. In various example embodiments, eachgesture of the various gestures 608 has an initial point, current point,and terminal point. As shown in the diagram 600, an example gesture ofthe various gestures 608 has initial point 610, current point 612, andterminal point 614. In an embodiment, the initial point 610 is alocation on the touchscreen 602 where the user 604 first made physicalcontact to initiate a particular gesture. Although, in otherembodiments, the initial point 610 is not necessarily the location atwhich the user 604 first made physical contact, but may be a location atwhich the user 604 initiated a particular gesture (e.g., via a press andhold gesture). For instance, the user first makes initial contact withthe touchscreen 602 at a particular point and executes a hold gesture atanother point on the touchscreen 602 while remaining in continuousphysical contact with the touchscreen 602. In this instance, the initialpoint is the point or location at which the user executed the holdgesture to initiate the radial slide gesture and is not necessarily thepoint where the user first made contact with the touchscreen 602(although in some cases the point of first contact by the user is thesame point as where the hold gesture is performed by the user). Thecurrent point 612 is the location on the touchscreen 602 where the user604 is currently making physical contact with the touchscrecn 602. Asshown in the diagram 600, the current point 612 can be co-located withthe touch 606. The terminal point 614 is the location on the touchscreen602 where the user 604 terminates or completes a particular gesture. Forexample, the user 604 terminates a particular gesture by releasing orlifting their finger or stylus from the touchscreen 602. The terminalpoint will coincide with the current point at a moment in time when thegesture is terminated.

Turning again to FIG. 4, at operation 440, the gesture module 230determines a radius distance based on the initial point and the currentpoint. In an example embodiment, the radius distance is a radius of acircle that includes the current point and is centered about the initialpoint. The radius distance is independent of angular information. Thatis to say, the angle formed between a reference line and a lineextending through the initial point and the current point has no bearingon the radius distance. Put another way, the user can perform the radialslide gesture at a variety of angles with respect to a reference line ofthe display to select the same action since the distance of the radialslide gesture is determinative of the action and not necessarily theangle at which the radial slide gesture is performed.

At operation 450, the action module 240 selects an action from amongmultiple actions based on the radius distance, or radial distance, beingwithin a particular range among successive ranges along a straight linethat starts at the initial point and extends through the circle. Forexample, the action module 240 accesses a lookup table (stored locallyat the user device or remotely at a server) that includes actionscorresponding to particular radius distances and identifies the actionfor the radius distance by performing a lookup for a particular actionusing the determined radius distance. In some embodiments, the actionmodule 240 performs the lookup of the action using a piece of dataextracted from the user input data (e.g., the designated user interfaceelement that indicates a member of the social messaging service) inconjunction with the radius distance to determine the action.

In further embodiments, the action module 240 receives or detects anindication of a designated user interface element. For instance, thegesture module 230 may detect the indication of the designated userinterface element based on the initial point (e.g., the user interfaceelement corresponding to the initial point). In other embodiments, theuser specifies the designated user interface element, or multipledesignated user interface elements, prior to performing the radial slidegesture. For instance, the user may select one or multiple items from aparticular list and subsequently perform the radial slide gesture toinvoke an action associated with the selected items. In a specificexample, the user may select multiple individuals on a friends list andsubsequently perform the radial slide gesture to initiate a group chator identify those individuals as favorites among those on the friendslist.

In various embodiments, the action module 240 identifies candidateactions available for a particular designated user interface element anddynamically determines the successive ranges for each of the candidateactions. For example, if the designated user interface element is anindividual on a friends list of the user, the action module 240 mayidentify available communication modalities with the individual (e.g.,the action module 240 may indicate that text-based chatting and textmessaging are available but video or voice communications are notcurrently available for the individual). In this example, the actionmodule 240 identifies the available communication modalities as thecandidate actions. In other embodiments, the multiple actions arepredefined for a type of designated user interface element or for aparticular user interface. For instance, the multiple actions cancomprise text messaging, voice streaming, or video streaming, for aparticular designated user interface element that is associated with amember of the social messaging service.

In an example embodiment, each range among the successive rangescorresponds to a particular action among the multiple actions. In anexample embodiment, the successive ranges are a series of consecutiveranges along a straight line. Since the successive ranges areindependent of angular information, the successive ranges can also beconceptualized as regions formed by concentric circle boundaries. Thatis to say, the concentric circles are the boundaries for the successiveranges. In some instances, the length of each of the successive rangesis uniform. In other embodiments, the length of each of the successiveranges is not necessarily uniform. For example, each range of thesuccessive ranges may become larger, or smaller, (e.g., exponentiallywith respect to distance from the initial point) as the range becomesfurther away from the initial point (e.g., the widest range beingfurthest from the initial point).

In some embodiments, the lengths of the successive ranges arepredefined. In other embodiments, the action module 240 determines thelength of each of the successive ranges dynamically. For example, theaction module 240 determines the length of a particular range based onthe initial point. In a specific example, if an initial point is nearthe edge of a display, the action module 240 may utilize ranges oflonger length as there is more space (in the direction away from theedge) for the user to perform the radial slide gesture. In anotherexample, the action module 240 determines the lengths of respectiveranges of the successive ranges based on the designated user interfaceelement. For instance, the designated user interface element may beassociated with a certain set of actions, and the action module 240determines the lengths of ranges based on a count of actions in the setof actions.

In further embodiments, the action module 240 determines the radiusdistance is within a no-action range. For example, the no-action rangeextends from the initial point to a specified distance. While the radiusdistance is within the no-action range, the action module does notselect an action to perform. The purpose of the no-action range is toprovide a way for the user to cancel or stop the radial slide gesturefrom performing an action. Thus, the invocation module 250 performs noaction in response to detecting the termination or completion of thecontinuous physical user interaction while the radius distance is withinthe no-action range. In other embodiments, the no-action range could bebeyond the edge of the display or an actual radial distance (e.g.,0.25-0.3 inches).

To illustrate the concepts of operations 440 and 450. FIG. 7 is adiagram 700 depicting various gestures on an example touchscreen 702. Itwill be appreciated that the illustrative elements of the diagram 700are shown for the purposes of understanding the concepts describedherein and are not shown to the user. That is to say, touch data 710,712, and 714 are used by the gesture navigation system 160 internallyand the regions, arrows, and graphs of the diagram 700 are forillustrative purposes and are not part of a particular user interface.As shown in the diagram 700, example gestures 704, 706, and 708 arerespectively associated with the touch data 710, 712, and 714. Forexample, the touch data 710 for the gesture 704 shows a graph ofdistance versus time, the distance in the graph for the touch data 710being the distance between the initial point and the current point. Asindicated by the touch data 710, at first, the distance changes verylittle with time, and then the distance changes at a fairly steady ratewith time. Such touch data (e.g., touch data 710) may be characteristicof the hold gesture immediately followed by the radial slide gesture.The gesture module 230 detects various characteristics or attributes ofthe gesture from touch data such as the touch data 710.

In various embodiments, the gesture module 230 determines the radiusdistance of the radial slide gesture, and the action module 240 selectsa particular action based on the determined radius distance. Forexample, areas or regions 716, 718, and 720 with boundaries 722, 724,726, and 728 may each correspond to a different action. In a specificexample, the action module 240 selects a particular action correspondingto the region 718 when the radius distance falls between the boundaries722 and 726. In this example, the user interface module 220 causespresentation of a visual indication of the available action for theregion 718 (e.g., a textual or graphical description of what the actiondoes). The purpose of the visual indication is to convey to the userwhat the currently selected action does to assist the user in decidingwhether to perform the currently selected action. The multiple actionsmay include a wide variety of different actions that can be performedlocally at the user device, remotely at a particular server, or acombination thereof. For example, the multiple actions includefavoriting, liking, tagging, deleting or removing from a list,reordering a list, making a purchase, selecting an option for aparticular purchase, sending a message, initiating a chat session,modifying an image captured by the user device, altering a system oruser interface preference or option (e.g., a quality of a video render),and so on.

Returning to FIG. 4, at operation 460, the invocation module 250performs the selected action in response to detecting a termination ofthe continuous physical user interaction while the radius distance iswithin the particular range for the selected action. The invocationmodule 250 can perform or facilitate performing the action locally atthe user device or remotely by exchanging information with anotherserver, device, or system. In a specific example, the invocation module250 establishes a chat session between the user of the user device andanother member of the social messaging service. In various embodiments,the user interface module 220 causes presentation of an indication thatindicates a successful or failed completion or invocation of theselected action in response to the invocation module 250 successfully orunsuccessfully invoking the selected action.

FIG. 8 is a flow diagram 800 illustrating example operations forpresenting a visual indication of an action associated with a gesture.As described above, at operation 420, the gesture module 230 detects aninitial point from the user data. Subsequently, at operation 430, thegesture module 230 detects a current point from the user input data. Insome embodiments, the operations of FIG. 8 are performed subsequent tothe operation 430.

At operation 810, the gesture module 230 determines when the radiusdistance of the radial slide gesture transgresses a particular boundaryfor a particular range among the successive ranges. That is to say, whenthe path of the radial slide gesture falls within a new range of thesuccessive ranges (shown as “yes” in the diagram 800), the userinterface module 220 causes presentation of a visual indicationassociated with the new range. Conversely, if the gesture module 230determines the radius distance has not transgressed the particularboundary, then the gesture navigation system 160 simply proceeds tooperation 440 (shown as “no” in the diagram 800) skipping operating 820.

At operation 820, after the gesture module 230 determine the radiusdistance transgresses the particular boundary, the user interface module220 causes presentation of a visual indication of the selected action inresponse to the current point transgressing a boundary of the particularrange. For example, the visual indication may indicate a function of anaction associated with the new range (e.g., textual or graphicaldescription of the action). In an embodiment, the visual indicationremains on the display while the action is available to the user (e.g.,until the user moves the touch to transgress another boundary or untilthe user completes the radial slide gesture by, for example, releasingtheir finger from the touchscreen).

In some embodiments, the user interface module 220 causes presentationof a visual indication on the user interface of the user device thatindicates the selected action cannot be performed or that no action canbe performed. For example, the action module 240 may determine thatthere are no actions available for a particular designated userinterface element and in response to this determination, the userinterface module 220 presents the visual indication to indicate that noactions can be performed. In another example, the action module 240determines that a particular action among the multiple actions is notavailable to be performed, and in response to this determination, theuser interface module 220 presents a visual indicate to indicate thatthe particular action cannot be performed.

FIG. 9 is a user interface diagram 900 depicting an example visualindication 920 of an action displayed on an example touchscreen 910. Inan example embodiment, the user interface module 220 causes presentationof the visual indication 920 overlaid on top of a user interface of thetouchscreen 910. In some embodiments, the user interface module 220 doesnot obscure a portion of the user interface or a particular userinterface element with the visual indication 920. For instance, adesignated user interface element 930 may remain unobscured by thevisual indication 920, as shown in the diagram 900.

In further embodiments, the user interface module 220 deactivates aportion of the user interface, or at least one user interface element ofthe user interface, after detecting the initial point or when the radialslide gesture is initiated to prevent user interaction with thedeactivated portion of the user interface. This is to prevent undesiredinteraction with user interface elements while the user is performingthe radial slide gesture.

FIG. 10 is a flow diagram 1000 illustrating example operations fordetecting certain aspects of a gesture. As described above, at operation410, the sensor module 260 receives the user input data. At operation420, the gesture module 230 detects the initial point from the userdata. In some embodiments, operation 420 includes the additionaloperations of FIG. 10.

At operation 1010, the gesture module 230 detects a hold gesture at theinitial point from the user input data. For instance, the hold gesturecan comprise the user touching the touchscreen at a particular locationand substantially refraining from moving the current point of the touchfor a threshold period of time.

At operation 1020, the gesture module 230 determines if a thresholdperiod of time has expired. In various embodiments, after the gesturemodule 230 determines the threshold period of time has expired, theradial slide gesture is initiated (shown as “yes” in the diagram 1000)or, stated another way, a radial slide mode begins. If the thresholdperiod of time has not expired and the user has either terminated thehold gesture (e.g., lifting the user's finger from the touchscreen) ormoved the current point away from the initial point (e.g., moved by morethan a hold threshold distance), the gesture navigation system 160 doesnot perform subsequent operations and returns to operation 410 toreceive more user input data (shown as “no” in the diagram 1000). Insome instances, the user performs the radial slide gesture 350 as acontinuation of, or in succession of, the hold gesture (e.g., the userremains in continuous physical contact with the touchscreen throughoutthe hold gesture and the radial slide gesture 350). The purpose of firstinitiating the radial slide gesture is to prevent undesired userinterface interaction and allow the user to normally interact with theunderlying user interface. Once the radial slide mode is initiated, thegesture module 230 can detect the current point from the user input dataat the operation 430, as shown in the diagram 1000.

To illustrate the concepts of FIG. 10, FIG. 11 is a user interfacediagram 1100 depicting example data used to detect a radial slidegesture 1120 at a touchscreen 1110. The regions 1130, 1140, and 1150correspond to different actions that the user can select by performingthe radial slide gesture 1120. In some embodiments, the user can performthe radial slide gesture 1120 outward from the initial point and thenreturn inward towards the initial point to cycle to a previous action.As described above for other illustrative figures, it will beappreciated that the illustrative elements of the diagram 1100 are shownfor the purposes of understanding the concepts described herein and arenot shown to the user. That is to say, the touch data 1160 is used bythe gesture navigation system 160 internally and the regions, arrows,and graphs of the diagram 1100 are for illustrative purposes and are notpart of a particular user interface. The touch data 1160 shows exampleuser input data that the sensor module 260 may receive in response tothe gesture 1120. Graph line 1162 (the dotted line in the graph of thetouch data 1160) shows the change in the radius distance of the radialslide gesture 1120 versus time. Threshold 1164 is a time threshold. Forexample, the gesture module 230 may first detect a hold gesture prior todetecting an instance of a radial slide gesture (e.g., the radial slidegesture 350, 1120 as described above). As shown by the touch data 1160,if the graph line 1162 remains substantially in the same location forthe threshold 1164 period of time, the gesture module 230 detects thehold gesture and proceeds to detect the radial slide gesture 1120. Thethresholds 1166, 1168, and 1170 are distance thresholds that correspondto the region 1130, 1140, and 1150. As shown by the touch data 1160, theradial slide gesture 1120 was terminated or completed in-between thedistance threshold 1168 and 1170, which corresponds to an actionassociated with the region 1140.

FIG. 12 is a user interface diagram 1200 depicting an example ofperforming an action associated with an item 1204 that is shown on atouchscreen 1202 using a radial slide gesture 1206. The touchscreen 1202may display an article, digital magazine story, or another piece ofdigital media from a digital media channel. In an example embodiment,the user can interact with a particular item from the digital media viathe radial slide gesture 1206. For example, the user may wish topurchase a particular item shown in the touchscreen 1202. In the diagram1200, the user can initiate a purchase flow by touching and holding theitem in the touchscreen 1202 at a location of the item of interest(e.g., the item 1204) and subsequently performing the radial slidegesture 1206. In an embodiment, different attributes of the purchase(e.g., quantity, color, size, using a particular payment account to payfor the purchase) can be selected based on the radius distance of theradial slide gesture 1206. For example, if the user completes the radialslide gesture 1206 within the boundaries of 1208 and 1210, the user mayinitiate a purchase flow for the item with least expensive options(e.g., slowest shipping and fewer accessories). In another example, ifthe user completes the radial slide gesture 1206 outside the boundary1210, the user may initiate a purchase flow for the item with moreexpensive options (e.g., a fastest shipping or, in the case of concerttickets, better seating). Accordingly, the radial slide gesture 1206provides a high degree of interactivity with the digital media withoutvisually obscuring the content of the digital media.

FIG. 13 is a user interface diagram 1300 depicting an example use caseof the techniques described above. In the diagram 1300, a user 1304performs a physical touch 1306 at a particular point on a touchscreendisplay 1302. For example, the touchscreen display 1302 may bedisplaying digital media such as a digital magazine article, a video, aphotograph, a text message, an interactive webpage, or another type ofdigital media. In these examples, the user 1304 performs an actionassociated with the digital media by performing a hold gesture followedby a radial slide gesture 1308. For instance, the user 1304 physicallytouches anywhere on the digital media and substantially refrains frommoving the current point of the physical touch for a threshold period oftime (e.g., 0.75 seconds), and then performs the radial slide gesture1308 to select a particular action. In a specific example, the user 1304invokes an action such as favoriting, sharing, or sending to friends orcontacts on the social messaging service the digital media by performingthe slide gesture 1308 to within a particular range such as indicated byfavorite 1310 and share 1312. In this way, the user 1304 can share aparticular piece of digital media by directly interacting with thedigital media on the touchscreen display 1302.

FIG. 14 is a diagram 1400 illustrating an optional example embodiment ofinitiating a live video stream of media data being captured in real timeby a user device 1420 of a user 1410. Although the diagram 1400 depictsthe gesture navigation system 160 in the social messaging system 130, inother example embodiments, the gesture navigation system 160, or aportion of the gesture navigation system 160, can be implemented in theuser device 1420. In embodiments where the user device 1420 includes aportion of the gesture navigation system 160, the user device 1420 canwork alone or in conjunction with the portion of the gesture navigationsystem 160 included in a particular application server or included inthe social messaging system 130.

In the diagram 1400, the user device 1420 is capturing media data from asensor of the user device 1420 that is communicatively coupled to thesocial messaging system 130 via the network 104. The media datacomprises, for example, audio data alone, video data alone, audio/videodata, or other data of the user device 1420. For instance, theaudio/video data is captured by a camera sensor and a microphone of theuser device 1420. In various example embodiments, the user device 1420records the audio/video data meaning that the user device 1420 storesthe audio/video data locally at the user device 1420, remotely at thesocial messaging system 130, or at a particular third-party server. Theuser 410 can initiate a live stream (e.g., a live broadcast) of thecaptured audio/video by performing a gesture 1440 with a physical touch1430 on a touchscreen of the user device 1420. In some exampleembodiments, the user 1410 switches between a recording mode orrecording session that records the audio/video data and a streaming modeor live streaming session that live steams the audio video data to aplurality of other user devices 1450. For instance, the user 1410switches from a recording mode to a live streaming mode by performingthe gesture 1440 while the user device 1420 is currently in therecording mode.

In various example embodiments, the live stream of the audio/video databeing captured by the device 1420 is communicated or transmitted to thesocial messaging system 130 and subsequently communicated, transmitted,or broadcast to the plurality of other user devices 1450 via the network104. In an example embodiment, the plurality of other user devices 1450includes devices of particular members of the social messaging system130. In some embodiments, the particular members of the social messagingsystem are friends or contacts of the user 1410 on the social messagingsystem 130. In other embodiments, the particular members of the socialmessaging system are subscribed to receive the live stream of theaudio/video data being captured by the user device 1420 (e.g.,subscribed to a particular channel where the live stream is available).In further example embodiments, the live stream is publicly available,exclusively available to certain users, or a combination thereof.

In various example embodiments, the live stream is being broadcast insubstantially real time. A real time stream or live stream is intendedto include streams that are delivered (e.g., received and presented to aparticular device) to a destination (e.g., the plurality of other userdevices 1450) after a delay interval (e.g., due to transmission delay orother delays such as being temporarily stored at an intermediate device)between the instant that the audio/video data is captured by the userdevice 1420 and a delivery time that the audio/video data is deliveredto the destination. For instance, the audio/video data being captured bythe user device 1420 and live streamed to the plurality of other userdevices 1450 can be buffered at the user device 1420, at the socialmessaging system 130, or another intermediate device and delivered tothe destination after a buffering delay.

In some example embodiments, the user device 1420 is live streaming theaudio/video data and recording the audio/video data at the same time. Inother example embodiments, the user device 1420 is live streaming theaudio/video data without the audio/video data being recorded or stored.In these embodiments, the gesture navigation system 160 or the socialmessaging system 130 provides the user 1410 with an option to store thestreamed audio/video data during the live streaming session or after thelive streaming session is over. For instance, the user 1410 may initiatelive streaming only of the audio/video data and then select an option tostore or discard the audio/video data that was live streamed after thelive streaming session has stopped.

FIG. 15 is a flow diagram illustrating an example method 1500 forswitching between a recording session and live streaming session. Theoperations of method 1500 are performed by components of the gesturenavigation system 160, and are so described below for the purposes ofillustration.

At operation 1510, similar to operation 410 described above inconnection with FIG. 4, the sensor module 260 receives user input datathat indicates a continuous physical user interaction (a gesture)associated with a display screen of the user device. For example, theuser performs a gesture or a combination of gestures such as a press andhold gesture followed by a slide or drag gesture on a touch-sensitivedisplay of a mobile device of the user. In a specific example, the userperforms a hold gesture on a particular user interface element on atouchscreen of the user device.

At operation 1520, the invocation module 250 initiates a recordingsession. For example, the gesture module 230 extracts a gesturecharacteristic from the user input data (e.g., a particular userinterface element designated by a hold gesture), the action module 240selects an action to initiate the recording session based on theextracted gesture characteristic, and then the invocation module 250invokes or initiates the recording session. The recording sessionrecords or stores media data captured by one or more sensors of the userdevice such as a microphone and a camera sensor. The media data cancomprise audio/video recording, audio only recording, video onlyrecording, or recording of data from another device sensor or otherdevice data (e.g., user interface image data that is currently beingdisplayed on the user device). In an example embodiment, the media datais stored locally on the user device, remotely on a server, or acombination thereof.

At operation 1530, the sensor module 260 receives user additional userinput data that indicates a slide gesture. For example, the userperforms the slide gesture in succession to the hold gesture describedabove in operation 1510.

At operation 1540, the gesture module 230 extracts a gesturecharacteristic of the slide gesture from the additional user input data.In an example embodiment, the slide gesture is the radial slide gestureas described above. In this embodiment, gesture module 230 extracts theradius distance or radial distance from the slide gesture. In anotherembodiment, the slide gesture designates a particular user interfaceelement. For example, the gesture module 230 designates the particularuser interface element in response to determining the slide gestureterminated (e.g., the user lifting their finger from the touchscreen orthe user refraining from moving the current point of the slide gesturefor a threshold period of time) at the particular user interfaceelement.

At operation 1550, the action module 240 determines the extractedgesture characteristic satisfies a condition and the invocation module250 initiates a live streaming session. The invocation module 250invokes or initiates the live streaming session that broadcasts,transmits, or otherwise communicates the media data being captured bythe user device to other user devices (e.g., the plurality of other userdevices 1450). For example, if the gesture characteristic is a radiusdistances and the action module 240 determines the radius distance iswithin a range corresponding to a live stream action, the invocationmodule 250 initiates the live streaming session. In another example, ifthe gesture characteristic is a designated user interface elementcorresponding to a live stream action, the invocation module 250initiates the live streaming session.

FIG. 16 is a user interface diagram 1600 depicting an example ofinitiating a recording session with an option to switch to a livestreaming session. In the diagram 1600, a user 1604 performs a physicaltouch 1614 of a touchscreen 1602. In an example embodiment, the sensormodule 260 receives the user input data resulting from the physicaltouch 1614 and the gesture module 230 extracts a gesture characteristicfrom the user input data, the action module 240 identifies a particularaction based on the gesture characteristic, and the invocation module250 invokes the particular action.

In a specific example, the user 1604 activates a user interface element1616 by performing the physical touch 1614 at an area encompassed by theuser interface element 1616. In this example, activating the userinterface element 1616 initiates the recording session or recording modeand the media data captured by the user device is stored or recorded. Inan example embodiment, the user interface module 220 causes presentationof an indication 1606 that indicates a current mode of the user device.

In various example embodiments, after the invocation module 250initiates the recording session, the user interface module 220 causespresentation of various user interface elements 1608 corresponding tooptions. For instance, a user interface element 1610 corresponds to anoption to initiate a streaming session during the recording session. Inan example embodiment, the user 1604 performs a slide gesture 1612 toone of the various user interface elements 1608 to invoke a particularaction. The user interface module 220 can cause presentation of thevarious user interface elements 1608 according to a predefined scheme ordynamically based on the user input data. For example, the userinterface module 220 can arrange the various user interface elements1608 to encircle an initial point of a particular gesture. In furtherexample embodiments, the user interface module 220 may modify thearrangement of the various user interface elements 1608 based on howclose the initial point of the gesture is to the edge of the touchscreen1602 or another characteristic extracted from the user input data. Invarious example embodiments, each of the various user interface elements1608 includes an indication of an action. The action module 240 maydynamically determine the action corresponding to respective ones of thevarious user interface elements 1608 (e.g., based on a user interfaceelement designated by an initial point of a particular gesture).

FIG. 17 is a user interface diagram 1700 depicting an example ofswitching from a recording session to a streaming session. In thediagram 1700, a user 1704 performs a physical touch 1710 of atouchscreen 1702. As the user 1704 moves the current point of thephysical touch 1710 towards a user interface element 1708, the userinterface module 220 alters or modifies the user interface element 1708.For example, the user interface module 220 changes an opacity, a color,or a size of the user interface element 1708 based on a distance betweenthe current point of the physical touch 1710 and the position of theuser interface element 1708 on the touchscreen 1702. In furtherembodiments, the user interface module 220 causes presentation ofinformation associated with the live streaming session such asconnectivity information of the user device (e.g., signal strength,roaming, connection speed, and so on) and may provide an indication ofwhether the invocation module 250 can initiate the live streamingsession based on the connectivity information. In the diagram 1700, theuser 1704 designates the user interface element 1708 to initiate astreaming session. For example, the user 1704 performs a slide gesturefrom user interface element 1712 to the user interface element 1708 toswitch from the recording session to the streaming session. In someexample embodiments, the user interface module 220 causes presentationof an indication 1706 of the current mode of the user device such asbeing in a streaming session.

FIG. 18 is a user interface diagram 1800 depicting an example ofinitiating a sustained recording session with a gesture 1810. In thediagram 1800, a user 1804 performs a gesture 1810 with a physical touch1808 of a touchscreen 1802. In an example embodiment, the gesturenavigation system 160 detects various combinations of gestures of theuser 1804 to initiate a recording session and adjust parameters of therecording session. For example, the user 1804 touching and holding auser interface element 1806 initiates the recording session while theuser 1804 holds down on the user interface element 1806. The user 1804terminates the recording session by ending the hold (e.g., lifting theuser's 1804 finger from the touchscreen 1802). In some embodiments, theuser 1804 ‘locks’ the recording session (a sustained recording sessionthat does not terminate by lifting the user's 1804 finger from thetouchscreen 1802) by performing an upward slide gesture, such as thegesture 1810, on the touchscreen 1802 after initiating the recordingsession. For instance, if the gesture module 230 detects the user 1804performing a slide gesture with a slide distance greater than aparticular threshold (an example threshold is indicated by point 1812 ofFIG. 18) then the action module 240 selects an action to initiate thesustained recording session and the invocation module 250 initiates thesustained recording session.

In still further embodiments, the user 1804 adjusts, alters, orotherwise modifies parameters or settings of the recording session, suchas a zoom level, by performing a slide gesture along an axis (e.g., ahorizontal slide, a vertical slide, or a slide along another axis)subsequent to initiating the sustained recording session. For instance,the user 1804 sliding to point 1814 zooms out while the user 1804sliding to point 1816 zooms in. In a specific example, the user 1804performs a hold gesture of the user interface element 1806 to initiatethe recording session, performs an upward slide gesture to initiate thesustained recording session, and then performs a horizontal slidegesture to zoom in or zoom out.

FIG. 19 is a flow diagram 1900 illustrating an example method foradjusting, altering, or otherwise modifying parameters, characteristics,or settings of the recording session, the live streaming session, or amedia presentation session via a particular gesture. The operations ofmethod 1900 are performed by components of the gesture navigation system160, and are so described below for the purposes of illustration.

At operation 1910, similar to operation 410 and operation 1510 describedabove, the sensor module 260 receives user input data that indicates acontinuous physical user interaction or gesture associated with adisplay screen of the user device. For example, the sensor module 260detects the user performing a particular gesture comprising a physicallytouch, or multiple physical touches, on the touchscreen of the userdevice.

At operation 1920, the gesture module 230 extracts a gesturecharacteristic of the particular gesture from the user input data. Forexample, the gesture module 230 determines an axis distance of theparticular gesture such as a distance between an initial point of thegesture and a current point of the gesture along a particular axis(e.g., a horizontal distance, a vertical distance, or a distance alonganother axis).

At operation 1930, the action module 240 determines an action based onthe gesture characteristic and the invocation module 250 invokes theaction. For example, the action can comprise modifying a videocharacteristic or attribute of a video such as a zoom level, videoquality level, camera focus, camera exposure setting, flash settings,switching between available cameras, and so forth. In a specificexample, the action module 240 determines a zoom level according to theaxis distance. For instance, the action module 240 determines that theaction comprises an increase in zoom level corresponding to an increasein the axis distance and a decrease in zoom level corresponding to adecrease in the axis distance.

FIG. 20 is a user interface diagram 2000 depicting an example ofinitiating the live streaming session and modifying a characteristic ofthe live streaming session via a particular gesture. In the diagram2000, a user 2004 initiates a live streaming session by performing agesture 2010 comprising a physical touch 2012 on a touchscreen 2002. Forexample, the user 2004 may perform the gesture 2010, such as the radialslide gesture describe above, to select an option to initiate arecording session 2008 or a live streaming session 2006. In thisexample, the user 2004 selects the option to initiate a live streamingsession 2006 by terminating the gesture 2010 at the point 2014 (e.g.,the user 2004 lifting their finger from the touchscreen 2002 at thepoint 2014 or holding at the point 2014 for a threshold period of time).Subsequently, the user 2004 can perform a slide gesture in succession tothe radial slide gesture to adjust a zoom level of the video for thelive stream. For instance, the user 2004 sliding across the touchscreen2002 towards the point 2016 zooms out and sliding towards point 2018zooms in. In this way, the gesture navigation system 160 detectsmultiple gestures allowing the user 2004 to adjust various settings ofthe live streaming session.

FIG. 21 is a user interface diagram 2100 depicting a further example ofadjusting, altering, or otherwise modifying parameters, characteristics,or settings of the recording session, the live streaming session, or amedia presentation session via a particular gesture. In the diagram2100, a user 2104 is performing a particular gesture comprising physicaltouch 2110 and physical touch 2108. The user 2104 performs a holdgesture with the physical touch 2110 by substantially refraining frommoving the physical touch 2110 from point 2112. While the user 2104 isperforming the hold gesture with the physical touch 2110, the user 2104performs a vertical slide gesture, or a slide gesture along anotheraxis, by moving the physical touch 2108 vertically. In an exampleembodiment, sliding the physical touch 2108 towards point 2118 zooms outwhile sliding the physical touch 2108 towards point 2116 zooms in. Thepurpose of using the hold gesture in conjunction with the vertical slidegesture is to help prevent undesired user interaction (e.g., anaccidental touch of the touchscreen by the user 2104). Although, inalternative example embodiments, the user 2104 performs the slidegesture to effectuate zooming, or another type of adjustment, withoutperforming the hold gesture with the physical touch 2110. In theseembodiments, the user 2104 effectuates zooming of the video using asingle finger.

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules can constitute eithersoftware modules (e.g., code embodied on a machine-readable medium) orhardware modules. A “hardware module” is a tangible unit capable ofperforming certain operations and can be configured or arranged in acertain physical manner. In various example embodiments, one or morecomputer systems (e.g., a standalone computer system, a client computersystem, or a server computer system) or one or more hardware modules ofa computer system (e.g., a processor or a group of processors) can beconfigured by software (e.g., an application or application portion) asa hardware module that operates to perform certain operations asdescribed herein.

In some embodiments, a hardware module can be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware module can include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware module can be a special-purpose processor, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC). A hardware module may also includeprogrammable logic or circuitry that is temporarily configured bysoftware to perform certain operations. For example, a hardware modulecan include software executed by a general-purpose processor or otherprogrammable processor. Once configured by such software, hardwaremodules become specific machines (or specific components of a machine)uniquely tailored to perform the configured functions and are no longergeneral-purpose processors. It will be appreciated that the decision toimplement a hardware module mechanically, in dedicated and permanentlyconfigured circuitry, or in temporarily configured circuitry (e.g.,configured by software) can be driven by cost and time considerations.

Accordingly, the phrase “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein.“hardware-implemented module” refers to a hardware module. Consideringembodiments in which hardware modules are temporarily configured (e.g.,programmed), each of the hardware modules need not be configured orinstantiated at any one instance in time. For example, where a hardwaremodule comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware modules) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware module at one instance oftime and to constitute a different hardware module at a differentinstance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules can be regarded as being communicatively coupled. Where multiplehardware modules exist contemporaneously, communications can be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware modules. In embodiments inwhich multiple hardware modules are configured or instantiated atdifferent times, communications between such hardware modules may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware modules have access.For example, one hardware module can perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module can then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules can also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein can beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors constitute processor-implemented modulesthat operate to perform one or more operations or functions describedherein. As used herein. “processor-implemented module” refers to ahardware module implemented using one or more processors.

Similarly, the methods described herein can be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method can be performed by one or more processors orprocessor-implemented modules. Moreover, the one or more processors mayalso operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an Application ProgramInterface (API)).

The performance of certain of the operations may be distributed amongthe processors, not only residing within a single machine, but deployedacross a number of machines. In some example embodiments, the processorsor processor-implemented modules can be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented modules are distributed across a number ofgeographic locations.

The modules, methods, applications and so forth described in conjunctionwith FIGS. 1-21 are implemented in some embodiments in the context of amachine and an associated software architecture. The sections belowdescribe representative software architecture and machine (e.g.,hardware) architecture that are suitable for use with the disclosedembodiments.

Software architectures are used in conjunction with hardwarearchitectures to create devices and machines tailored to particularpurposes. For example, a particular hardware architecture coupled with aparticular software architecture will create a mobile device, such as amobile phone, tablet device, and the like, while yet another combinationproduces a server computer for use within a cloud computingarchitecture. Not all combinations of such software and hardwarearchitectures are presented here as those of skill in the art canreadily understand how to implement the inventive subject matter indifferent contexts from the disclosure contained herein.

FIG. 22 is a block diagram 2200 illustrating a representative softwarearchitecture 2202, which may be used in conjunction with varioushardware architectures herein described. FIG. 22 is merely anon-limiting example of a software architecture and it will beappreciated that many other architectures may be implemented tofacilitate the functionality described herein. The software architecture2202 may be executing on hardware such as machine 2300 of FIG. 23 thatincludes, among other things, processors 2310, memory/storage 2330, andI/O components 2350. A representative hardware layer 2204 is illustratedand can represent, for example, the machine 2300 of FIG. 23. Therepresentative hardware layer 2204 comprises one or more processingunits 2206 having associated executable instructions 2208. Executableinstructions 2208 represent the executable instructions of the softwarearchitecture 2202, including implementation of the methods, modules andso forth of FIGS. 1-21. Hardware layer 2204 also includes memory andstorage modules 2210, which also have executable instructions 2208.Hardware layer 2204 may also comprise other hardware 2212 whichrepresents any other hardware of the hardware layer 2204, such as theother hardware illustrated as part of machine 2300.

In the example architecture of FIG. 22, the software architecture 2202may be conceptualized as a stack of layers where each layer providesparticular functionality. For example, the software architecture 2202may include layers such as an operating system 2214, libraries 2216,frameworks/middleware 2218, applications 2220 and presentation layer2244. Operationally, the applications 2220 or other components withinthe layers may invoke application programming interface (API) calls 2224through the software stack and receive a response, returned values, andso forth illustrated as messages 2226 in response to the API calls 2224.The layers illustrated are representative in nature and not all softwarearchitectures have all layers. For example, some mobile or specialpurpose operating systems may not provide the frameworks/middleware2218, while others may provide such a layer. Other softwarearchitectures may include additional or different layers.

The operating system 2214 may manage hardware resources and providecommon services. The operating system 2214 may include, for example, akernel 2228, services 2230, and drivers 2232. The kernel 2228 may act asan abstraction layer between the hardware and the other software layers.For example, the kernel 2228 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 2230 may provideother common services for the other software layers. The drivers 2232may be responsible for controlling or interfacing with the underlyinghardware. For instance, the drivers 2232 may include display drivers,camera drivers. BLUETOOTH® drivers, flash memory drivers, serialcommunication drivers (e.g., Universal Serial Bus (USB) drivers), WI-FI®drivers, audio drivers, power management drivers, and so forth dependingon the hardware configuration. In an example embodiment, the operatingsystem 2214 includes sensor service 2233 that can provide various sensorprocessing services such as low-level access to touchscreen input dataor other user sensor data.

The libraries 2216 may provide a common infrastructure that may beutilized by the applications 2220 or other components or layers. Thelibraries 2216 typically provide functionality that allows othersoftware modules to perform tasks in an easier fashion than to interfacedirectly with the underlying operating system 2214 functionality (e.g.,kernel 2228, services 2230 or drivers 2232). The libraries 2216 mayinclude system libraries 2234 (e.g., C standard library) that mayprovide functions such as memory allocation functions, stringmanipulation functions, mathematic functions, and the like. In addition,the libraries 2216 may include API libraries 2236 such as medialibraries (e.g., libraries to support presentation and manipulation ofvarious media format such as MPREG4, H.264. MP3, AAC, AMR. JPG, or PNG),graphics libraries (e.g., an OpenGL framework that may be used to render2D and 3D in a graphic content on a display), database libraries (e.g.,SQLite that may provide various relational database functions), weblibraries (e.g., WebKit that may provide web browsing functionality),and the like. The libraries 2216 may also include a wide variety ofother libraries 2238 to provide many other APIs to the applications 2220and other software components/modules. In an example embodiment, thelibraries 2216 include input libraries 2239 that provide input tracking,capture, or otherwise monitor user input such as touchscreen input thatcan be utilized by the gesture navigation system 160.

The frameworks/middleware 2218 (also sometimes referred to asmiddleware) may provide a higher-level common infrastructure that may beutilized by the applications 2220 or other software components/modules.For example, the frameworks/middleware 2218 may provide various graphicuser interface (GUI) functions, high-level resource management,high-level location services, and so forth. The frameworks/middleware2218 may provide a broad spectrum of other APIs that may be utilized bythe applications 2220 or other software components/modules, some ofwhich may be specific to a particular operating system or platform. Inan example embodiment, the frameworks/middleware 2218 include an imagetouch input framework 2222 and a motion capture framework 2223. Thetouch input framework 2222 can provide high-level support for touchinput functions that can be used in aspects of the gesture navigationsystem 160. Similarly, the motion capture framework 2223 can providehigh-level support for motion capture and other input user inputdetection.

The applications 2220 include built-in applications 2240 or third partyapplications 2242. Examples of representative built-in applications 2240may include, but are not limited to, a contacts application, a browserapplication, a book reader application, a location application, a mediaapplication, a messaging application, or a game application. Third partyapplications 2242 may include any of the built-in applications 2240 aswell as a broad assortment of other applications. In a specific example,the third party application 2242 (e.g., an application developed usingthe ANDROID™ or IOS™ software development kit (SDK) by an entity otherthan the vendor of the particular platform) may be mobile softwarerunning on a mobile operating system such as IOS™, ANDROID™, WINDOWS®Phone, or other mobile operating systems. In this example, the thirdparty application 2242 may invoke the API calls 2224 provided by themobile operating system such as operating system 2214 to facilitatefunctionality described herein. In an example embodiment, theapplications 2220 include a messaging application 2243 that includes thegesture navigation system 160 as part of the messaging application 2243.In another example embodiment, the applications 2220 include astand-alone application 2245 that includes the gesture navigation system160.

The applications 2220 may utilize built-in operating system functions(e.g., kernel 2228, services 2230 or drivers 2232), libraries (e.g.,system libraries 2234, API libraries 2236, and other libraries 2238),frameworks/middleware 2218 to create user interfaces to interact withusers of the system. Alternatively, or additionally, in some systemsinteractions with a user may occur through a presentation layer, such aspresentation layer 2244. In these systems, the application/module“logic” can be separated from the aspects of the application/module thatinteract with a user.

Some software architectures utilize virtual machines. In the example ofFIG. 22, this is illustrated by virtual machine 2248. A virtual machinecreates a software environment where applications/modules can execute asif they were executing on a hardware machine (such as the machine 2300of FIG. 23, for example). The virtual machine 2248 is hosted by a hostoperating system (operating system 2214 in FIG. 23) and typically,although not always, has a virtual machine monitor 2246, which managesthe operation of the virtual machine 2248 as well as the interface withthe host operating system (i.e., operating system 2214). A softwarearchitecture executes within the virtual machine 2248 such as anoperating system 2250, libraries 2252, frameworks/middleware 2254,applications 2256 or presentation layer 2258. These layers of softwarearchitecture executing within the virtual machine 2248 can be the sameas corresponding layers previously described or may be different.

FIG. 23 is a block diagram illustrating components of a machine 2300,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically. FIG. 23 shows a diagrammatic representation of the machine2300 in the example form of a computer system, within which instructions2316 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 2300 to perform any oneor more of the methodologies discussed herein can be executed. Forexample, the instructions 2316 can cause the machine 2300 to execute theflow diagrams of FIGS. 4, 8, 10, 15, and 19. Additionally, oralternatively, the instructions 2316 can implement the communicationmodule 210, the user interface module 220, the gesture module 230, theaction module 240, the invocation module 250, or the sensor module 260of FIG. 2, and so forth. The instructions 2316 transform the general,non-programmed machine into a particular machine programmed to carry outthe described and illustrated functions in the manner described. Inalternative embodiments, the machine 2300 operates as a standalonedevice or can be coupled (e.g., networked) to other machines. In anetworked deployment, the machine 2300 may operate in the capacity of aserver machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 2300 can comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a set-top box (STB), apersonal digital assistant (PDA), an entertainment media system, acellular telephone, a smart phone, a mobile device, a wearable device(e.g., a smart watch), a smart home device (e.g., a smart appliance),other smart devices, a web appliance, a network router, a networkswitch, a network bridge, or any machine capable of executing theinstructions 2316, sequentially or otherwise, that specify actions to betaken by the machine 2300. Further, while only a single machine 2300 isillustrated, the term “machine” shall also be taken to include acollection of machines 2300 that individually or jointly execute theinstructions 2316 to perform any one or more of the methodologiesdiscussed herein.

The machine 2300 can include processors 2310, memory/storage 2330, andI/O components 2350, which can be configured to communicate with eachother such as via a bus 2302. In an example embodiment, the processors2310 (e.g., a Central Processing Unit (CPU), a Reduced Instruction SetComputing (RISC) processor, a Complex Instruction Set Computing (CISC)processor, a Graphics Processing Unit (GPU), a Digital Signal Processor(DSP), an Application Specific Integrated Circuit (ASIC), aRadio-Frequency Integrated Circuit (RFIC), another processor, or anysuitable combination thereof) can include, for example, processor 2312and processor 2314 that may execute instructions 2316. The term“processor” is intended to include multi-core processor that maycomprise two or more independent processors (sometimes referred to as“cores”) that can execute instructions contemporaneously. Although FIG.23 shows multiple processors 2310, the machine 2300 may include a singleprocessor with a single core, a single processor with multiple cores(e.g., a multi-core processor), multiple processors with a single core,multiple processors with multiples cores, or any combination thereof.

The memory/storage 2330 can include a memory 2332, such as a mainmemory, or other memory storage, and a storage unit 2336, bothaccessible to the processors 2310 such as via the bus 2302. The storageunit 2336 and memory 2332 store the instructions 2316 embodying any oneor more of the methodologies or functions described herein. Theinstructions 2316 can also reside, completely or partially, within thememory 2332, within the storage unit 2336, within at least one of theprocessors 2310 (e.g., within the processor's cache memory), or anysuitable combination thereof, during execution thereof by the machine2300. Accordingly, the memory 2332, the storage unit 2336, and thememory of the processors 2310 are examples of machine-readable media.

As used herein, the term “machine-readable medium” means a device ableto store instructions and data temporarily or permanently and mayinclude, but is not be limited to, random-access memory (RAM), read-onlymemory (ROM), buffer memory, flash memory, optical media, magneticmedia, cache memory, other types of storage (e.g., Erasable ProgrammableRead-Only Memory (EEPROM)) or any suitable combination thereof. The term“machine-readable medium” should be taken to include a single medium ormultiple media (e.g., a centralized or distributed database, orassociated caches and servers) able to store instructions 2316. The term“machine-readable medium” shall also be taken to include any medium, orcombination of multiple media, that is capable of storing instructions(e.g., instructions 2316) for execution by a machine (e.g., machine2300), such that the instructions, when executed by one or moreprocessors of the machine 2300 (e.g., processors 2310), cause themachine 2300 to perform any one or more of the methodologies describedherein. Accordingly, a “machine-readable medium” refers to a singlestorage apparatus or device, as well as “cloud-based” storage systems orstorage networks that include multiple storage apparatus or devices. Theterm “machine-readable medium” excludes signals per se.

The I/O components 2350 can include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific IOcomponents 2350 that are included in a particular machine will depend onthe type of machine. For example, portable machines such as mobilephones will likely include a touch input device or other such inputmechanisms, while a headless server machine will likely not include sucha touch input device. It will be appreciated that the I/O components2350 can include many other components that are not shown in FIG. 23.The I/O components 2350 are grouped according to functionality merelyfor simplifying the following discussion, and the grouping is in no waylimiting. In various example embodiments, the IO components 2350 caninclude output components 2352 and input components 2354. The outputcomponents 2352 can include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 2354 can include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstruments), tactile input components (e.g., a physical button, a touchscreen that provides location and force of touches or touch gestures, orother tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 2350 can includebiometric components 2356, motion components 2358, environmentalcomponents 2360, or position components 2362 among a wide array of othercomponents. For example, the biometric components 2356 can includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 2358 can includeacceleration sensor components (e.g., an accelerometer), gravitationsensor components, rotation sensor components (e.g., a gyroscope), andso forth. The environmental components 2360 can include, for example,illumination sensor components (e.g., a photometer), temperature sensorcomponents (e.g., one or more thermometers that detect ambienttemperature), humidity sensor components, pressure sensor components(e.g., a barometer), acoustic sensor components (e.g., one or moremicrophones that detect background noise), proximity sensor components(e.g., infrared sensors that detect nearby objects), gas sensorcomponents (e.g., machine olfaction detection sensors, gas detectionsensors to detect concentrations of hazardous gases for safety or tomeasure pollutants in the atmosphere), or other components that mayprovide indications, measurements, or signals corresponding to asurrounding physical environment. The position components 2362 caninclude location sensor components (e.g., a Global Positioning System(GPS) receiver component), altitude sensor components (e.g., altimetersor barometers that detect air pressure from which altitude may bederived), orientation sensor components (e.g., magnetometers), and thelike.

Communication can be implemented using a wide variety of technologies.The I/O components 2350 may include communication components 2364operable to couple the machine 2300 to a network 2380 or devices 2370via a coupling 2382 and a coupling 2372, respectively. For example, thecommunication components 2364 include a network interface component orother suitable device to interface with the network 2380. In furtherexamples, communication components 2364 include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, BLUETOOTH®components (e.g., BLUETOOTH® Low Energy), WI-FI® components, and othercommunication components to provide communication via other modalities.The devices 2370 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a UniversalSerial Bus (USB)).

Moreover, the communication components 2364 can detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 2364 can include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as a Universal Product Code (UPC) barcode, multi-dimensional bar codes such as a Quick Response (QR) code.Aztec Code, Data Matrix, Dataglyph. MaxiCode, PDF417. Ultra Code,Uniform Commercial Code Reduced Space Symbology (UCC RSS)-2D bar codes,and other optical codes), acoustic detection components (e.g.,microphones to identify tagged audio signals), or any suitablecombination thereof. In addition, a variety of information can bederived via the communication components 2364, such as location viaInternet Protocol (IP) geo-location, location via WI-FI® signaltriangulation, location via detecting a BLUETOOTH® or NFC beacon signalthat may indicate a particular location, and so forth.

In various example embodiments, one or more portions of the network 2380can be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the PublicSwitched Telephone Network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a WI-FI®network, another type of network, or a combination of two or more suchnetworks. For example, the network 2380 or a portion of the network 2380may include a wireless or cellular network, and the coupling 2382 may bea Code Division Multiple Access (CDMA) connection, a Global System forMobile communications (GSM) connection, or other type of cellular orwireless coupling. In this example, the coupling 2382 can implement anyof a variety of types of data transfer technology, such as SingleCarrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized(EVDO) technology. General Packet Radio Service (GPRS) technology,Enhanced Data rates for GSM Evolution (EDGE) technology, thirdGeneration Partnership Project (3GPP) including 3G, fourth generationwireless (4G) networks. Universal Mobile Telecommunications System(UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability forMicrowave Access (WiMAX). Long Term Evolution (LTE) standard, othersdefined by various standard setting organizations, other long rangeprotocols, or other data transfer technology.

The instructions 2316 can be transmitted or received over the network2380 using a transmission medium via a network interface device (e.g., anetwork interface component included in the communication components2364) and utilizing any one of a number of well-known transfer protocols(e.g., Hypertext Transfer Protocol (HTTP)). Similarly, the instructions2316 can be transmitted or received using a transmission medium via thecoupling 2372 (e.g., a peer-to-peer coupling) to devices 2370. The term“transmission medium” shall be taken to include any intangible mediumthat is capable of storing, encoding, or carrying the instructions 2316for execution by the machine 2300, and includes digital or analogcommunications signals or other intangible medium to facilitatecommunication of such software.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Although an overview of the inventive subject matter has been describedwith reference to specific example embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader scope of embodiments of the present disclosure. Such embodimentsof the inventive subject matter may be referred to herein, individuallyor collectively, by the term “invention” merely for convenience andwithout intending to voluntarily limit the scope of this application toany single disclosure or inventive concept if more than one is, in fact,disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, modules, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations may be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource may be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of embodiments of thepresent disclosure as represented by the appended claims. Thespecification and drawings arc, accordingly, to be regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A method comprising: capturing, by one or moreprocessors, live media data from a camera sensor of a user device;displaying the live media data on a touchscreen of the user device;detecting a first gesture on the touchscreen while displaying the livemedia data, the first gesture corresponding to a first plurality ofcontinuous touch positions along a first direction; sending a livestream of the live media data to other user devices in response to afirst distance of the plurality of continuous touch positions along thefirst direction performed by the first gesture exceeding a threshold;detecting, while sending the live stream of the live media data to theother user devices, a second gesture on the touchscreen having a seconddistance, the second gesture corresponding to a second plurality ofcontinuous touch positions along a second direction, the seconddirection corresponding to a different axis than the first direction;and adjusting a zoom level of the live stream based on the seconddistance of the second gesture, the zoom level being adjusted by thesecond plurality of continuous touch positions along the seconddirection after the live stream is initiated by the first plurality ofcontinuous touch positions along the first direction.
 2. The method ofclaim 1, wherein the first gesture comprises a touch and hold gesture,the detecting the first gesture comprising: detecting a plurality ofcontinuous touch positions of physical contact between an object and thetouchscreen including an initial position and a second position, theplurality of continuous touch positions including the first plurality ofcontinuous touch positions along the first direction, the plurality ofcontinuous touch positions immediately following the touch and holdgesture without interruption of touch contact, wherein the firstdistance is a distance between the initial position and the secondposition; and immediately following the first plurality of continuoustouch positions, detecting the second gesture comprising hg secondplurality of continuous touch positions starting from the secondposition and ending at a third position, wherein the second plurality ofcontinuous touch positions are along h second direction, and the seconddistance is a distance between the second position and the thirdposition.
 3. The method of claim 2, further comprising selecting anaction based on the first distance, the selection independent of anangle of a line formed by the continuous touch positions and a referenceline of the touchscreen.
 4. The method of claim 3, wherein the object isa finger of a user, and the method further comprises: determining thatthe finger of the user has been lifted from the touchscreen; and causingpresentation of a user interface on the user device, the user interfacedisplaying a visual indication of the selected action.
 5. The method ofclaim 4, wherein the visual indication is overlaid on top of the userinterface obscuring a portion of the user interface.
 6. The method ofclaim 2, further comprising: deactivating at least one user interfaceelement after detecting the initial position to prevent user interactionwith the at least one user interface element.
 7. The method of claim 1,further comprising: detecting, from touchscreen input data, a holdgesture based on continuous contact at a particular position for athreshold period of time.
 8. The method of claim 1, further comprising:determining the first distance is below a specified distance; andperforming no action in response to the determination that the firstdistance is below the specified distance.
 9. The method of claim 1,further comprising: receiving an indication of a designated userinterface element, wherein each of multiple actions is associated withthe designated user interface element.
 10. The method of claim 9,further comprising: determining the designated user interface elementbased on the first gesture.
 11. The method of claim 9, wherein thedesignated user interface element is not obscured by a visual indicationassociated with a selected action of the multiple actions.
 12. Themethod of claim 11, further comprising: causing presentation of a visualindication on a user interface that the selected action cannot beperformed.
 13. The method of claim 1, switching between a recordingsession and the live stream based on a distance associated with thefirst plurality of continuous touch position.
 14. The method of claim13, further comprising causing the live media data to be recorded duringthe recording session in response to determining that the firstplurality of continuous touch positions ended within a first distance ofinitial contact with the touchscreen, and activating the live stream inresponse to determining that the first plurality of continuous touchpositions ended within a second distance of the initial contact with thetouchscreen.
 15. The method of claim 1, further comprising: causingdisplay of a user interface element corresponding to activation of thelive stream; and modifying a display attribute of the user interfaceelement based on a distance between a current position associated withthe first gesture and a position of the user interface element on thetouchscreen.
 16. The method of claim 1, further comprising causingpresentation of information associated with the live stream, theinformation comprising connectivity information and an indication thatthe connectivity information allows the live stream to be sent to theother user devices.
 17. A non-transitory machine-readable medium storinginstructions that, when executed by at least one hardware processor,configure the at least one hardware processor to perform a method, themethod comprising: capturing live media data from a camera sensor of auser device; displaying the live media data on a touchscreen of the userdevice; detecting a first gesture on the touchscreen while displayingthe live media data the first gesture corresponding to a first pluralityof continuous touch positions along a first direction; sending a livestream of the live media data to other user devices in response to afirst distance of the plurality of continuous touch positions performedby the first gesture exceeding a threshold; detecting, while sending thelive stream of the live media data to the other user devices, a secondgesture on the touchscreen having a second distance, the second gesturecorresponding to a second plurality of continuous touch positions alonga second direction, the second direction corresponding to a differentaxis than the first direction; and adjusting a zoom level of the livestream based on the second distance of the second gesture.
 18. Thenon-transitory machine-readable medium of claim 17, wherein the firstgesture comprises a touch and hold gesture, the detecting the firstgesture comprising: detecting a plurality of continuous touch positionsof physical contact between an object and the touchscreen including aninitial position and a second position, the plurality of continuoustouch positions including the first plurality of continuous touchpositions along the first direction, the plurality of continuous touchpositions immediately following the touch and hold gesture withoutinterruption of touch contact, wherein the first distance is a distancebetween the initial position and the second position; and immediatelyfollowing the first plurality of continuous touch positions, detectingthe second gesture comprising the second plurality of continuous touchpositions starting from the second position and ending at a thirdposition, wherein the second plurality of continuous touch positions arealong the second direction, and the second distance is a distancebetween the second position and the third position.
 19. A systemcomprising: one or more processors configured to perform operationscomprising: capturing live media data from a camera sensor of a userdevice; displaying the live media data on a touchscreen of the userdevice; detecting a first gesture on the touchscreen while displayingthe live media data, the first gesture corresponding to a firstplurality of continuous touch positions along a first direction; sendinga live stream of the live media data to other user devices in responseto a first distance of the plurality of continuous touch positionsperformed by the first gesture exceeding a threshold; detecting, whilesending the live stream of the live media data to the other userdevices, a second gesture on the touchscreen having a second distance,the second gesture corresponding to a second plurality of continuoustouch positions along a second direction, the second directioncorresponding to a different axis than the first direction; andadjusting a zoom level of the live stream based on the second distanceof the second gesture.
 20. The system of claim 19, wherein the firstgesture comprises a touch and hold gesture, the detecting the firstgesture comprising: detecting a plurality of continuous touch positionsof physical contact between an object and the touchscreen including aninitial position and a second position, the plurality of continuoustouch positions including the first plurality of continuous touchpositions along the first direction, the plurality of continuous touchpositions immediately following the touch and hold gesture withoutinterruption of touch contact, wherein the first distance is a distancebetween the initial position and the second position; and immediatelyfollowing the first plurality of continuous touch positions, detectingthe second gesture comprising the second plurality of continuous touchpositions starting from the second position and ending at a thirdposition, wherein the second plurality of continuous touch positions arealong the second direction, and the second distance is a distancebetween the second position and the third position.